Enabling enterprise segmentation with 5G slices in a service provider network

ABSTRACT

An enterprise controller of an enterprise network sends to a service gateway of a service provider network a request for network slice information about network slices provisioned on a data plane of the service provider network. Responsive to the sending, the enterprise controller receives from the service gateway the network slice information including identifiers of and properties associated with the network slices. Responsive to receiving a request for the network slice information from a network device at a border of a forwarding plane of the enterprise network, the enterprise controller sends the network slice information to the network device to cause the network device to perform configuring network traffic in the forwarding plane with identifiers of ones of the network slices that match the network traffic, and to perform forwarding the network traffic configured with the identifiers to the data plane of the service provider network.

TECHNICAL FIELD

The present disclosure relates to enabling enterprise networksegmentation with 5G slices in a service provider network.

BACKGROUND

Today an enterprise, i.e., an enterprise network, increasingly offloadsits infrastructure into the public cloud. With the arrival of 5Gnetworks, it is predicted that billions of devices will be added tonetwork edges, which are part of fixed or mobile networks. The deviceswill be operating across multiple network domains, all which may besegmented for services of the network domains, not only across the 5Gnetworks but also extended through to the enterprise network.

Due to these changes, major services or applications running on publicor private clouds, such as machine-to-machine (m2m) and data in-and-dataout of data centers, are projected to grow. This will bring scalabilitylimitations for m2m communication and for mission critical applicationsdue to the lack of service policy enforcement and segmentation. Some ofthese applications require differentiated transport services, e.g.,packet latency, packet loss, packet jitter, packet disjointedness,packet replication, and packet segmentation. As devices are connectedacross heterogeneous networks, transport and segmentation services forthe devices should be provided end-to-end (e2e) across the networkdomains.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a conceptualized illustration of 5G network slicing that maybe applied to different types of network traffic of an enterprisenetwork, according to an example embodiment.

FIG. 2 is a block diagram of an enterprise 5G Network-as-a-Service(NaaS), including an enterprise network and a service provider (SP)network, in which embodiments presented herein may be implemented,according to an example embodiment.

FIG. 3 is a block diagram that shows components of the enterprisenetwork and the SP network, and various message exchanges between thecomponents, employed to create 5G slices and to use the 5G slicesbetween the enterprise network and the SP network, according to anexample embodiment.

FIG. 4 shows operations directed to network slice creation andenterprise use performed by the components of FIG. 3, according to anexample embodiment.

FIG. 5 shows operations directed to network slice creation andenterprise use performed by the components of FIG. 3, according toanother embodiment.

FIG. 6 is a block diagram that shows components of the enterprisenetwork and the SP network, and various message exchanges between thecomponents, employed to implement user group to policy distribution fromthe enterprise network to the SP network, according to an exampleembodiment.

FIG. 7 shows example operations directed to user group to policydistribution from the enterprise network to the SP network performed bythe components of FIG. 6, according to an example embodiment.

FIG. 8 is a block diagram that shows components of the enterprisenetwork and the SP network, and various message exchanges between thecomponents, employed to implement mobile device identity distributionfrom the enterprise network to the SP network, according to an exampleembodiment.

FIG. 9 shows operations directed to mobile device identity distributionfrom the enterprise network to the SP network performed by thecomponents of FIG. 8, according to an example embodiment.

FIG. 10 is a block diagram of the enterprise network and the SP networkthat shows a combination of the components and the message transactionsshown in FIGS. 3-9, according to an example embodiment.

FIG. 11 is a diagram of detailed message flows or transactions betweenthe enterprise network and the SP network, according to an exampleembodiment.

FIG. 12 is a block diagram of a network device configured to performtechniques described herein, according to an example embodiment.

FIG. 13 is a block diagram of a controller device configured to performtechniques presented herein, according to an example embodiment.

FIG. 14 is a flowchart of a method performed primarily by enterprisecontroller, according to an example embodiment.

FIG. 15 is an illustration of an Internet Protocol (IP) packet forwardedfrom a forwarding plane of the enterprise network after an enterprisecontroller of the enterprise network has configured the IP packet,according to an example embodiment.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

An enterprise controller of an enterprise network sends to a servicegateway of a service provider network a request for network sliceinformation about network slices provisioned on a data plane of theservice provider network. Responsive to the sending, the enterprisecontroller receives from the service gateway the network sliceinformation including identifiers of the network slices and propertiesassociated with the network slices. Responsive to receiving a requestfor the network slice information from a network device at a border of aforwarding plane of the enterprise network, the enterprise controllersends the network slice information to the network device to cause thenetwork device to perform configuring network traffic in the forwardingplane with identifiers of ones of the network slices that match thenetwork traffic, and to perform forwarding the network trafficconfigured with the identifiers of the ones of the network slices to thedata plane of the service provider network.

Example Embodiments

Third (3^(rd)) Generation Partnership Project (3GPP) 5G (hereinafter“5G”) holds the promise of “network slicing” to provide 5G networkslices (referred to simply as “slices”), which may be applied to a levelof granularity of an enterprise network. Therefore, there is anopportunity to extend enterprise network segments of the enterprisenetwork to service provider 5G slices, so that the enterprise networkcan leverage service provider 5G infrastructure, to extend enterprisenetwork segments to remote sites and cloud environments, end-to-endacross the heterogeneous networks. Embodiments presented herein provideways to extend enterprise transport services and segmentation over theservice provider 5G slices.

Before delving into how the enterprise network segments aremapped/carried using service provider 5G slices, 5G network slicing isdescribed briefly. Service provider 5G network slicing enables a serviceprovider to build virtual end-to-end networks tailored to applicationrequirements. At the service provider, a network core that supports 5Gvirtualization uses 5G network slicing to support multiple virtualnetworks over a physical infrastructure or data plane. The data plane,also referred as the forwarding plane, is the part of a network thatcarries/routes/forwards user traffic. 5G network slicing permits alogical separation of a physical network into distinct (virtualized) 5Gslices so that each slice provides unique connectivity characteristics,but all 5G slices run on the same shared physical networkinfrastructure. A given 5G slice supports a communication service of aparticular connection type with a specific way of handling the dataplane and the control plane for the service. Thus, 5G network slicingcreates unique services that are customized for various use cases suchas Internet of Things (IoT), automated cars, streaming video, remotehealth care, and so on. 5G network slicing creates virtual networks forapplications that require separate blends of performance, capacity,latency, security, reliability, and coverage, for example.

With reference to FIG. 1, there is a conceptualized illustration of 5Gnetwork slicing that may be applied to different types of enterprisenetwork traffic (simply referred to as “traffic”). The 5G networkslicing supports multiple concurrent protocol data unit (PDU)connections or sessions 102(1)-102(4) (collectively, “PDU sessions102”). The distribution of PDU sessions 102 is driven by enterpriseend-service and service application function requirements. PDU Sessions102 may be used when separate network anchor points are used. Each PDUsession 102(i) may support multiple quality of service (QoS) flows oftraffic. Each QoS flow may be associated with a distinct level of QoS.Thus PDU sessions 102 expose granularity of QoS management and trafficsegmentation to the enterprise network. 5G network slicing may apply aunique 5G slice for a given enterprise network customer for completecontrol of QoS flows, network anchor points, and trafficcharacteristics.

With reference to FIG. 2, there is a block diagram of an exampleenterprise 5G network as a service (NaaS) 200 (more simply referred toas a “network environment” 200) in which embodiments presented hereinmay be implemented. FIG. 2 shows extensions of services and functions ofan enterprise network 202 (shown primarily on the left-hand side of FIG.2) to a service provider (SP) network 204 (shown primarily in the middleand on the right-hand side of FIG. 2) that supports 5G network slicing.

Enterprise network 202 includes an access network 206, an enterprisedata plane 208 (also referred to as a “forwarding plane 208”), and anenterprise controller 210 to perform overall control of the enterprisenetwork, generally, and to control the access network and the dataplane. Access network 206 provides a mobile device 212 with access todata plane 208. Access network 206 includes an access point (AP) 214through which mobile device 212 accesses or attaches to the accessnetwork, and a wireless local area network (LAN) controller (WLC) 216 tocontrol the access point. In practice, access network 206 includes manymobile devices many APs, and many WLCs, although only one of each isshown in FIG. 2 for the sake of clarity. In practice, a fixed or mobiledevice is attached to an enterprise access network, e.g., the mobiledevice may be wirelessly attached or wired to access network 206.

Enterprise data plane 208 carries (user) traffic in the form of InternetProtocol (IP) packets to and from access network 206. Generally, dataplane 208 includes network devices, such as switches and routers. Dataplane 208 includes a switch fabric 218 comprising a fabric ofinterconnected switches (not specifically shown in FIG. 2), a fabricedge (FE) switch 220 connected to an edge of the switch fabric andaccess network 206, and a fabric border (FB) router 222 connected to anedge of the switch fabric (i.e., connected to a border of data plane208) and to service provider network 204. FE switch 220 switches thetraffic between access network 206 and switch fabric 218, switch fabric218 routes the traffic in data plane 208, and FB router 222 forwards thetraffic between the switch fabric and service provider network 204through a network 228, as described below. Network 228 may include oneor more wide area networks (WANs), such as the Internet, and one or moreLANs.

Enterprise controller 210 may be implemented as a Cisco digital networkarchitecture (DNA)-center (DNA-C), for example. Enterprise controller210 includes control plane applications, shown generally at cloud 234,configured to communicate with and assert control over access network206 and data plane 208. For example, control plane applications 230 mayselect segment routing (SR) services in data plane 208 for enterprisenetwork 202.

SP network 204 includes an SP data plane 231, an SP service gateway 232(also referred to simply as a “service gateway 232” of the SP network),and an SP SR controller, shown generally at cloud 234 (also referred tosimply as an “SR controller 234” of the SP network). SP service gateway232 performs access and session management operations for SP network204, communicates with enterprise controller 210 of enterprise network202 over a network, and communicates with other components andapplications of SP network 204, such as SP SR controller 234. SP servicegateway 232 acts as a conduit for messages, e.g., request and responses,between enterprise controller 210 and the other components andapplications of SP network 204, such as SP SR controller 234.

SP SR controller 234 manages 5G network slicing on SP data plane 231.For example, SP SR controller 234 provisions 5G slices on the SP dataplane 231 and maintains configuration information about the 5G slicesthat are provisioned, such as identifiers of the 5G slices andproperties associated with the 5G slices. Distinct properties of the 5Gslices may include latency, bandwidth, virtualized network function(VNF) service, and high quality service, to name a few. Thus, SP SRcontroller 234 manages SR for network service slices in SP data plane231. The VNF includes any function implemented by a dedicated systems(e.g., as shown in FIG. 12, described below) or virtualized on a generalcompute system (e.g., as shown in FIG. 13).

SP data plane 231 generally includes network devices, such as switchesand routers, to carry traffic received from and destined for data plane208 of enterprise network 202. SP data plane 231 implements 5G slicesunder control of SP SR controller 234, and applies the 5G slices to thetraffic as appropriate, as described below. SP data plane 231 may beextended to include a transport router 236 that communicates with acloud-based data center 238. SP data plane 231 includes an provider edgeor peer router 240 connected to network 228, a firewall 242 connected tothe provider edge router, and a core SP network 244 connected to thefirewall and network 228 and configured to implement 5G slices andsegment routing in the 5G slices.

Enterprise controller 210 and SP service gateway 232 employ distributedenterprise 5G service controller application specific interfaces (APIs)provided by an API engine 250 for (i) inter-network communication (e.g.,between enterprise network 202 and SP network 204), (ii) intra-networkcommunication (e.g., between SP service gateway 232 and SP SR controller234, and between SP service gateway 232 and transport router 236), and(iii) programming of functions in the SP network to support/extendenterprise network services across the SP network. More specifically,enterprise controller 210 employs an enterprise controller-to-SP gateway(GW) API 252 (also labeled “DNA-C to SP API GW,” in FIG. 2) tocommunicate with SP service gateway 232. SP service gateway 232 employsan API 254 (also labeled “SP API-GW”) to communicate with API 252 ofenterprise controller 210, an API 256 (also labeled “SP core API-GW”) tocommunicate with SP SR controller 234, and an API 258 (also labeled “SPtransport API-GW”) to communicate with transport router 236. APIs 254,256, and 258 communicate with each other. As indicated in FIG. 2, SPservice gateway 232 may employ API 254 to configure/program provideredge router 240 and firewall 242 as an SP/enterprise (ENT) (“SP/ENT”)demilitarized (network) zone (DMZ). Components/services/applicationsdesignated with the label “SP/ENT” in FIG. 2 indicates that thosecomponents/services/applications are extended across enterprise network202 and SP network 204. SP service gateway 232 may employ API 256 toprovision/program 5G slices on core network 244 to implement SP/ENTvirtual sessions and SP/ENT virtualization. SP service gateway 232 mayemploy API 258 to configure/program transport router 236 with an SP/ENTslice virtual topology.

Embodiments presented herein create different network constructs andapplications between control planes of enterprise network 202 and SPnetwork 204 to satisfy enterprise network requirements to be imposed ontraffic traversing SP data plane 231 of the SP network. The controlplanes include, for example, applications and protocols between networkdevices that determine paths in the data plane. At a high-level, theconstructs and applications include the following:

-   -   a. Network slice creation and enterprise use:        -   i. Creates a network association between enterprise network            202 and SP network 204.    -   b. User group to policy distribution from the enterprise network        to the SP network:        -   i. Performs management of profiles for enterprise user            groups and mapping of the user groups to network services.        -   ii. Maintains enterprise user group sessions in the SP            network to carry and apply enterprise user group specific            policy to traffic in the SP network.        -   iii. Maintains enterprise user group sessions in the SP            network for monitoring and billing of network usage by            traffic.    -   c. Mobile device identity distribution from the enterprise        network to the SP network:        -   i. Performs mobile device identity authentication between            the enterprise network and the SP network.

The embodiments that implement the above-listed constructs andapplications are presented in the context of 5G slicing and 5G slices byway of example, only. It is understood that the embodiments applyequally to other types of network slicing and network slices besides 5Gslicing and 5G slices, such as network slicing and network slicesdefined according to standards other than the 5G standards. For example,the embodiments apply, generally, to network slicing and network slicesthat support communication services of particular connection types withspecific ways of handling a data plane and a control plane for theservices. Generally, the network slicing creates unique servicescustomized for various use cases, and creates virtual networks forapplications that require separate blends of performance, capacity,latency, security, reliability, and coverage, for example.

Each of the above-listed constructs and applications are described inseries below. First, network slice creation and enterprise use isdescribed with reference to FIGS. 3-5.

FIG. 3 is a block diagram that shows components of enterprise network202 and SP network 204, and various messages exchanges between thecomponents, employed to create 5G slices and use the 5G slices betweenthe enterprise network and the SP network. FIG. 3 is also annotated toindicate various ones of operations of method 400 (i.e., 402-420)described below in connection with FIG. 4.

Enterprise controller 210 includes network service manager (NSM) 302 andan SP SR profile database (DB) 304 managed by the network servicemanager. Network service manager 302 may implemented as a virtualmachine (VM) or Linux container (LXC). FB router 222 includes a networkservice layer 306 configured with an SR service profile database, aforwarding information base 308, and forwarding logic 310, which may beimplemented in an application specific integrated circuit (ASIC), forexample.

SP data plane 231 may include a physical network infrastructure ofinterconnected switches and routers 312 configured to implement segmentrouting for 5G slices under control of SP SR controller 234.

FIG. 4 shows example operations of a method 400 (also designated in FIG.3) directed to network slice creation and enterprise use performed bythe components shown in FIG. 3, according to an embodiment. FIG. 4 isnow described with continued reference to FIG. 3. According tooperations of method 400, SP network 204 provisions/creates 5G slices onSP data plane 231 in real-time responsive to requests for the 5G slicesfrom/originated by enterprise controller 210, as described below.

At 402, in an a priori operation, enterprise controller 210 isprovisioned to request a 5G slice from SP network 204.

At 404, enterprise controller 210 (e.g., NSM 302) sends to SP servicegateway 232 a network segment request for a 5G slice. The request mayspecify properties for the 5G slice that satisfy/match enterprisenetwork requirements for traffic.

At 406, SP service gateway 232 receives the network segment request and,responsive thereto, sends a get/create network segment request to SP SRcontroller 234. The get network segment request may also specify theproperties of the 5G slice. Accordingly, at operations 402 and 404,enterprise controller 210 sends the network segment request to SP SRcontroller 234 through SP service gateway 232.

At 408, SP SR controller 234 receives the get network segment requestand, responsive thereto, provisions on SP data plane 231 a 5G slicehaving the properties as specified in the get network segment request.SP SR controller 234 also generates an identifier of the 5G slice thatis understood by the SP SR controller. The identifier represents an SRbinding segment/slice identifier (ID) (BSID) or “token” that referencesthe 5G slice, and binds the 5G slice to traffic in enterprise network202 (see operation 420 described below) and to segment routing used forthe 5G slice in SP data plane 231.

At 410, once SP SR controller 234 has provisioned the 5G slice on SPdata plane 231, the SP SR controller generates, and sends to SP servicegateway 232, a get network service response that includes the identifierof the 5G slice and the properties of the 5G slice.

At 412, SP service gateway 232 receives the get network segmentresponse, and forwards the response to enterprise controller 210.Enterprise controller 210 saves the identifier of the 5G slice and theproperties associated with the 5G slice in a network service profile inSP SR profile DB 304. Over time, multiple repetitions of operations 404through 412 store information for multiple 5G slices in the networkservice profile, including identifiers of the multiple 5G slices and theproperties of the 5G slices.

At 414, FB router 222 sends to enterprise controller 210 a networkservice request for the network service profile.

At 416, enterprise controller 210 receives from FB router 222 thenetwork service request and, responsive thereto, sends to FB router 222a network service response including the network service profile.

At 420, FB router 222 receives the network service response includingthe network service profile, and configures data plane 208 based on the5G slice information in the network service profile. Specifically, FBrouter 222 configures traffic traversing data plane 208 with particularones of the identifiers of the 5G slices that match the traffic. Toconfigure the traffic, FB router 222 first determines the particularones of the 5G slices that match the traffic based on a comparison oftraffic policies (e.g., level of QoS) associated with the traffic, asdefined in the enterprise network, and the properties associated withthe 5G slices (e.g., low latency, high bandwidth, VNF service, and soon). In other words, FB router 222 maps the 5G slices to the trafficbased on the properties of the 5G slices and the traffic policies. Then,FB router 222 applies the identifiers of the 5G slices to the trafficbased on results of the determining/mapping. For example, FB routerinserts the identifiers for the 5G slices into packet headers of IPpackets in the traffic. FB router 222 then forwards the trafficconfigured with the identifiers to SP data plane 231.

With reference to FIG. 5, there are shown example operations of method500 directed to network slice creation and enterprise use performed bythe components shown in FIG. 3, according to another embodiment.Operations of method 500 are similar to operations of method 400, exceptthat according to operations of method 500, SP network 204provisions/creates 5G slices on SP data plane 231 in an a prioroperation, and then returns information about the 5G slices toenterprise controller 210 responsive to a request for that informationfrom the enterprise controller, as described below. Operations 502-520correspond, more or less, with operations 402-420, respectively. FIG. 5is now described also with continued reference to FIG. 3.

At 501, in an a priori operation, SP SR controller 234 provisionsmultiple 5G slices on SP data plane 231. The 5G slices have respectiveidentifiers and properties associated with the 5G slices. In an example,the 5G slices may include a first slice configured to impose low latencyon traffic, a second slice configured for high bandwidth traffic, athird slice configured to provide VNF service for traffic, and a fourthslice configured to provide high quality service for traffic. That is,the low latency, the high bandwidth, the VNF service, and the highquality service represent the respective properties of the first,second, third, and fourth 5G slices, respectively. The 5G slices haverespective identifiers, i.e., 5G slice identifiers.

At 502, in an a priori operation, enterprise controller 210 isprovisioned to request information about the 5G slices from SP network204.

At 504, enterprise controller 210 sends to SP service gateway 232 anetwork segment request for the 5G slices provisioned on SP data plane231, i.e., for information about the 5G slices.

At 506, SP service gateway 232 receives the network segment request and,responsive thereto, sends a get network segment request to SP SRcontroller 234.

At 508, SP SR controller 234 receives the get network segment request.

At 510, responsive to the get network segment request, SP SR controller234 sends to SP service gateway 232, a get network service response thatincludes the respective identifiers of the 5G slices and theirproperties.

At 512, SP service gateway 232 receives the get network segment response(i.e., the information about the 5G slices that was previouslyrequested), and forwards the response to enterprise controller 210.Enterprise controller 210 saves the respective identifiers of the 5Gslices and their properties in the network service profile of SP SRprofile DB 304.

At 514, FB router 222 sends to enterprise controller 210 a networkservice request for the network service profile.

At 516, enterprise controller 210 receives from FB router 222 thenetwork service request and, responsive thereto, sends to FB router 222a network service response including the network service profile.

At 520, FB router 222 receives the network service response includingthe network service profile, and configures data plane 208 based on the5G slice information in the network service profile, as described abovein connection with operation 420. FB router 222 may configure differenttypes of traffic for the different types of 5G slices. For example, FBrouter 222 may configure (i) first QoS traffic (i.e., a first QoStraffic flow) with a first identifier of a 5G slice that matches thefirst QoS traffic, (ii) second QoS traffic with a second identifier of a5G slice that matches the second QoS traffic, and so on.

User group to policy distribution from enterprise network 202 to SPnetwork 204 is now described with reference to FIGS. 6 and 7.

FIG. 6 is a block diagram that shows components of enterprise network202 and SP network 204, and various message exchanges between thecomponents, employed to implement user group to policy distribution fromenterprise network 202 to SP network 204. FIG. 6 is also annotated withindicators of various ones of operations of method 700 (i.e., 702-708)described below in connection with FIG. 7.

As shown in FIG. 6, enterprise controller 210 includes user groupprofile manager (UGPM) 602 (also referred to as a “policy and assurancemanager”) in addition to network service manager 302 and an SP SRprofile DB 304, described above. User group profile manager 602 isprimarily responsible for user group to policy distribution, asdescribed below. Also, SP network 204 includes a policy, monitoring, andbilling manager 604 to map user group sessions to 5G slices and storeresulting mappings in a local database 606.

With reference to FIG. 7, there are shown example operations of method700 (also indicated in FIG. 6) directed to user group to policydistribution from enterprise network 202 to SP network 204 performed bythe components shown in FIG. 6, according to an embodiment. Operationsof method 700 assume that SP SR profile DB 304 stores information about5G slices provisioned on SP network 204. Such information may includefirst, second, third, and fourth 5G slice identifiers for latency,bandwidth, VNF service, and quality slices, acquired from operations502-512 described above. FIG. 7 is now described with continuedreference to FIG. 6.

At 702, enterprise controller 210 (e.g., UGPM 602) identifies enterprisenetwork user groups for groups users in enterprise network 202, andtraffic policies associated with the user groups. The traffic policiesare to be applied traffic associated with the user groups. The usergroups and the traffic policies may be provisioned on/defined byenterprise network 202 and stored in an enterprise network databaseaccessible to UGPM 602. The user groups are identified by respectiveuser group identifiers, e.g., security group tags (SGTs), and may belinked to respective ones of the traffic policies via respectiveidentifiers of the traffic policies. Enterprise controller 210determines user group-to-traffic policy mappings of the user groups tothe respective traffic polices associated with the user groups, andstores the user group-to-traffic policy mappings locally. In otherwords, enterprise controller 210 maps the user groups to the trafficpolicies associated with the user groups. The user group-to-trafficpolicy mappings may take the form of tuples [user group, trafficpolicy], for example. In this way enterprise controller 210binds/associates the user groups to/with their associated trafficpolicies.

At 704, enterprise controller 210 determines user group-to-5G slicemappings of (i.e., maps) the user groups to those 5G slices that matchthe user groups based on the traffic policies associated with the usergroups and the properties of the 5G slices. The user group-to-5G slicemappings may take the form of (identifier) tuples [user group, 5Gslice], for example. To perform the mapping, enterprise controller 210may compare the properties of the 5G slices provisioned on SP network204, as stored in SP SR profile DB 304, to the traffic policies, andthen perform the mapping based on results of the compare. For example, alow latency 5G slice would be deemed a match to a traffic policy thatrequires low latency, as indicated in a QoS value, and so on.

At 706, enterprise controller 210 sends to SP service gateway 232 a usergroup register request that includes the user group-to-traffic policymappings (i.e., first mappings [user group, traffic policy]) and theuser group-to-5G slice mappings (i.e., second mappings [user group, 5Gslice]). In response, SP service gateway 232 forwards to policy,monitoring, and billing (PMB) manager 604 a user group session createrequest accompanying the user group-to-traffic policy mappings (i.e.,first mappings) and the user group-to-5G slice mappings (i.e., secondmappings).

At 708, in response to receiving the mappings from SP service gateway232 sent at 706, PMB manager 604 stores the mappings in local database606, and configures/programs the associations indicated by the secondmappings [user group, 5G slice] into SP data plane 231, to ensuretraffic traversing SP network 204 experiences end-to-end consistentnetwork characteristics and performance. PMB manager 604 also uses thefirst mappings [user group, traffic policy] to establish enterprise usergroup sessions that monitor the traffic (e.g., traffic usage) traversingSP network 204 and apply billing services to the traffic consistent withthe user group and traffic policy associations, e.g., based on the firstmappings. PMB manager 604 also sends a user group session response toenterprise controller 210 through SP service gateway 232.

At 710, SP service gateway 232 sends to SP SR controller 234 the usergroup-to-traffic policy mappings (i.e., first mappings [user group,traffic policy]) and the user group-to-5G slice mappings (i.e., secondmappings [user group, 5G slice]). In response, at 712, SP SR controller234 programs/configures network devices of data plane 231 withinformation from the first and second mappings to enable/cause the dataplane to handle traffic from enterprise network 202 according to themappings. For example, SP service gateway 232 may program a provideredge router in data plane 231 (see, e.g., provider edge router PE1 ofFIG. 11, described below) with the first mappings and the secondmappings, so that the provider edge is able to (i) examine traffic fromenterprise network 202 for various indicators configured in the trafficby the enterprise network, e.g., for identifiers of user groups (e.g.,SGTs) and identifiers of 5G slices, and (ii) apply to the traffic thetraffic policies that correspond to the identifiers of the user groupsfound in the traffic according to the first mappings, (ii) and steer thetraffic to the 5G slices that correspond to the identifiers of the 5Gslices found in the traffic.

Thus, in operations 700, enterprise controller 210 sends to the firstmappings and the second mappings to control functions (e.g., SP SRcontroller 234 and PMB manager 604) of service provider network 204through/via SP service gateway 232. The control functions areresponsible for controlling and monitoring the network traffic (fromenterprise network 202) traversing data plane 208 of service providernetwork 204. The control functions perform the controlling andmonitoring based on the first mappings and the second mappings, i.e.,the first mappings and the second mappings cause the control functionsto perform the controlling and monitoring according to the firstmappings and the second mappings.

Mobile device (MD) identity distribution from enterprise network 202 toSP network 204 is now described with reference to FIGS. 8 and 9.

FIG. 8 is a block diagram that shows components of enterprise network202 and SP network 204, and various message exchanges between thecomponents, employed to implement mobile device identity distributionfrom enterprise network 202 to SP network 204. FIG. 8 is also annotatedto indicate various ones of operations 900 (i.e., 902-906) describedbelow in connection with FIG. 9. As shown in FIG. 8, enterprise network202 includes an identity services engine (ISE) 801 configured with amobility identity manager (also referred to as a “mobility identityregister”) that acquires mobile device identities from mobile devices,e.g., mobile device 212, and registers the mobile device identitieslocally. Enterprise controller 210 includes a mobility identity manager802, peered with the mobility identity manager of ISE 801, in additionto other components described above. Mobility identity manager 802maintains respective user mobile device identities for mobile devicesand also respective SP contexts associated with the mobile deviceidentities. Also, SP network 204 includes an identity-and-authenticationservice function/server (AUSF) (identity-and-AUSF) 804 to performauthentication of mobile devices and to register the mobile devices inSP network 204.

With reference to FIG. 9, there are shown example operations 900 (alsoindicated in FIG. 8) directed to mobile device identity distributionfrom enterprise network 202 to SP network 204 performed by thecomponents shown in FIG. 8. FIG. 9 is described with continued referenceto FIG. 8.

At 902, the mobile identity manager of ISE 801 learns a mobile deviceidentity of mobile device 212 at the location of enterprise network 202,registers the mobile device identity in the enterprise network, andpasses the mobile device identity to symmetric/peer mobility identitymanager 802 of enterprise controller 210. The mobile device identity isa unique identifier of the mobile device.

At 904, enterprise controller 210 (e.g., mobility identity manager 802)receives the mobile device identity. Enterprise controller 210 forwardsto identity-and-AUSF 804, through SP service gateway 232, a deviceidentity register request including the mobile device identity.Responsive to the request, identity-and-AUSF 804 authenticates mobiledevice 212 based on its mobile device identity, and registers the mobiledevice in SP network 204.

At 906, once the mobile device identity is registered in SP network 904,identity-and-AUSF 804 sends to mobility identity manger 802, through SPservice gateway 232, a device identity register response indicating themobile device identity was authenticated successfully and registered inSP network 204. Mobility identity manager 802 stores/maintains locallythe authenticated, registered device identity linked to an SP contextassociated with the identity, e.g., the indication that the identity wassuccessfully authenticated.

With reference to FIG. 10, there is a block diagram of enterprisenetwork 202 and SP network 204 that shows a combination of componentsand message transactions described above in connection with FIGS. 3-9.In other words, FIG. 10 shows components and message transactions ofenterprise network 202 and SP network 204 employed to implement (i)network slice creation and enterprise use, (ii) user group to trafficpolicy distribution from the enterprise network to the SP network, and(iii) mobile device identity distribution from the enterprise network tothe SP network.

FIG. 11 is a diagram of detailed message flows or transactions 1100(collectively referred to as transactions 1100) between enterprisenetwork 202 and the SP network 204. Transactions 1100 include variousones of the messages/transactions described above, primarily inconnection with the real-time provisioning and reporting of 5G slices ofmethod 400 of FIG. 4, with further details added to themessages/transactions. In FIG. 11, mobile device 212 has a source IPaddress A, and a device identity ID, and originates traffic destined foran endpoint device (i.e., “endpoint”) 1102 (shown at the lowerright-hand side of FIG. 12) having a destination IP address Z. FB router222 has an IP address designated as FB. FE 220 of data plane 208 is alsodesignated FE1. Also, SP data plane 231 includes a provider edge (PE)router PE1, a physical “SP network” 1106 corresponding to components 242and/or 244 of FIG. 2, and a provider edge router PE2 to communicate withendpoint 1102. SP network 204 includes a segment route comprisingnetwork devices S1, S2, and S3 configured to implement a provisioned 5Gslice having an identifier X, referred to in FIG. 11 as a bindingsegment ID (BSID) X.

Transactions 1106, 1108, and 1109 implement mobile device identitydistribution from enterprise network 202 to SP network 204, as describedabove in connection with FIGS. 8 and 9. In transactions 1106, 1108, and1109, “register: ID” represents the device identity register requestdescribed above, and “res” represents the device identity responsedescribed above. The request and response include the mobile deviceidentity ID.

Transaction 1110A, 1110B, and 1110C collectively represent a 5G slicerequest from FB router 222 to SP SR controller 234 that includes mobiledevice identity ID, source IP address FB, destination IP address Z, andan App designator. In an example, the App designator may include a QoSvalue for traffic to be handled by the requested 5G slice. The Appdesignator may be translated to an attribute designator Attr atenterprise controller 210. Transactions 1110A, 1110B, and 1110Ccorrespond generally to transactions 414, 404, and 410 described above,but in a permuted order.

Responsive to the 5G slice request, SP SR controller 234 performsfunction f (FB, Z, “Color”), which returns SR Policy (i.e., list ofsegment identifiers to visit) <BSID=X: S1, S2, S3, PE2>, in which S1 isthe first segment identifier to visit, S2 is the second segmentidentifier to visit, and S3 is the last segment identifier to visit. Thedesignator “Color” represents a transformation of the attribute Attr,which represents the designator App. In other words, the designatorColor maps back to the QoS value to be supported by the 5G slice. Thefunction determines/establishes the segment routing policy <X: S1, S2,S3> for the 5G slice. SP SR controller 234 configures the 5G slicehaving identifier BSID=X with segment route S1, S2, S3, exiting at PE2on SP data plane 231, to implement the required segment routing policytranslated from App. The configured routing may include, for example,Border Gateway Protocol (BGP) Link State (LS) (BGP-LS). SP SR controller234 configures provider edge router PE1 with 5G slice identifier BSID=Xand forwarding information to enable/cause PE1 to forward traffic tosegment route S1, S2, S3. Also, using transactions 1114A, 1114B, and1114C, which correspond generally to transactions 410, 412, and 416described above, SP SR controller 234 forwards to fabric border router222 a response to the 5G slice request. The response includesinformation for the 5G slice, such as identifier BSID=X and propertiesassociated with the 5G slice.

Responsive to receiving the 5G slice response including BSID=X, FBrouter 222 configures data plane 208 with BSID=X. To do this, FB router222 applies the following function to traffic traversing data plane 208:

f (ID, A, FB, Z, App), which returns SR (BSID:X),

where the control variables A, FB, Z, and App may be accessed fromheaders of IP packets in the traffic, and ID may be accessed fromenterprise controller 210.

The function returns BSID=X (i.e., the identifier of the 5G sliceprovisioned on SP data plane 231) responsive to the control variablesID, A, FB, Z, and App (e.g., QoS value) in the traffic. The functionmatches App (e.g., QoS value) in the traffic to the properties of the 5Gslice.

Armed with the identifier X of the 5G slice, FB router 222 configurestraffic according to the following rule: Traffic (A, BSID:X) (Z;Segments Left (SL)=1). In other words, FB router 222 inserts BSID=X intopacket headers of IP packets having source IP address A, and destinedfor endpoint Z. FB router 222 then forwards the configured traffic to SPnetwork 204.

Provider edge router PE1 receives the configured traffic from FB router222, and applies the following function to the traffic:

f (BSID:X), which returns SR Policy <S1, S2, S3, PE2>.

In other words, the provider edge router PE1 accesses the BSID (whichhas value X) from the packet headers of the traffic, and plugs the BSIDinto the function. In this case, BSID=X is mapped to segment router S1,S2, S3, exiting at PE2. Accordingly, provider edge router PE1 steers thetraffic to the segment route for the 5G slice with BSID=X, based on theBSID, according to the rule:

Traffic (PE1, S1)(PE2, S3, S2; SL=3) (A, Z)−>.

In other words, traffic with source IP address A and destination IPaddress Z is routed from PE1 to next hop S1; from there, the trafficreaches PE2 via S2 and S3.

While the transactions of FIG. 11 correspond primarily to the real-timeprovisioning and reporting of 5G slices of method 400, by way ofexample, slight modifications to the transactions may be made toimplement the a priori provisioning of 5G slices and then reporting ofthe 5G slices as described above in connection with method 500 of FIG.5. For example, SP SR controller 234 configures multiple 5G slices on SPdata plane 231 in an a prior operation, that preserves multiplecorresponding identifiers BSIDs, one per 5G slice, as described above.Then, responsive to a request “REQ” originated from FB router 222, andforwarded to SP SR controller 234, the SP SR controller returns theidentifiers BSIDs of the pre-provisioned 5G slices to the FB router,which applies the BSIDs to corresponding traffic flows destined from the5G slices.

With reference to FIG. 12, there is a block diagram of an examplenetwork device 1200 representative of a router or a switch (e.g., any ofthe routers and switches in enterprise network 202 and SP network 204),for example. Network device 1200 comprises a network interface unithaving a plurality of network input/output (I/O) ports 1242(1)-1242(M)to send traffic to and receive traffic from a network, and to forwardtraffic in the network, a packet forwarding/processing unit 1243, anetwork processor 1244 (also referred to simply as “processor”), and amemory 1246. The packet forwarding/processing unit 1243 is, for example,one or more application specific integrated circuits (ASICs) thatinclude packet buffers, packet queues, and other control logic forperforming packet forwarding operations. The processor 1244 may includemultiple processors, which may be implemented as software or hardwareprocessors. For example, processor 1244 may include a microcontroller ormicroprocessor that is configured to perform higher level controls ofnetwork device 1200. To this end, the memory 1246 stores softwareinstructions that, when executed by the processor 1244, cause theprocessor 1244 to perform a variety of operations including operationsdescribed herein. For example, the memory 1246 stores instructions forcontrol logic 1250 to perform operations described herein. Control logic1250 may also include logic components in packet forwarding unit 1243.

Memory 1246 also stores data 1260 used and generated by logic 1250,including packet loss information, for example.

With reference to FIG. 13, there is a block diagram of an examplecomputer device 1300 representative of controller devices (i.e.,controllers) or service gateways in enterprise network 202 and SPnetwork 204, such as enterprise controller 210, SP service gateway 232,SP SR controller 234, identity-and-AUSF 408, PMB manager 604, and so on.More generally, computer device 1300 may host control application andAPIs, such as API engine 250. Computer device 1300 includes networkinterface unit 1305 to communicate with a wired and/or wirelesscommunication network, and to control network devices over the network.Computer device 1300 also includes a processor 1354 (or multipleprocessors, which may be implemented as software or hardwareprocessors), and memory 1356. Network interface unit 1305 may include anEthernet card with a port (or multiple such devices) to communicate overwired Ethernet links and/or a wireless communication card with awireless transceiver to communicate over wireless links.

Memory 1356 stores instructions for implementing methods describedherein. Memory 1356 may include read only memory (ROM), random accessmemory (RAM), magnetic disk storage media devices, optical storage mediadevices, flash memory devices, electrical, optical, or otherphysical/tangible (non-transitory) memory storage devices. The processor1354 is, for example, a microprocessor or a microcontroller thatexecutes instructions stored in memory. Thus, in general, the memory1356 may comprise one or more tangible computer readable storage media(e.g., a memory device) encoded with software comprising computerexecutable instructions and when the software is executed (by theprocessor 1354) it is operable to perform the operations describedherein. For example, memory 1356 stores control logic 1358 to performoperations for controllers as described herein.

The memory 1356 may also store data 1360 used and generated by logic1358.

With reference to FIG. 14, there is a flowchart of an example method1400 performed primarily by enterprise controller 210. Method 1400includes operations described above.

At 1402, enterprise controller 210 sends to service gateway 232 ofservice provider network 204 a request for 5G slice information about 5Gslices provisioned on data plane 231 of the service provider network.

At 1404, responsive to the sending, enterprise controller 210 receives,from service gateway 232 the 5G slice information including identifiersof and properties associated with the 5G slices.

At 1406, responsive to receiving a request for the 5G slice informationfrom a network device (e.g., FB router 222) at a border of forwardingplane 208 of enterprise network 202, enterprise controller 210 sends the5G slice information to the network device to cause the network deviceto perform configuring network traffic in forwarding plane 208 with theidentifiers of particular ones of the 5G slices that match the networktraffic, and to perform forwarding the network traffic configured withthe identifiers to data plane 231 of service provider network 204.

With reference to FIG. 15, there is an illustration of an example IPpacket 1500 of traffic forwarded from forwarding plane 208 to SP dataplane 231, after enterprise controller 210 has configured the IP packetaccording to embodiments presented herein. IP packet 1500 includes oneor more headers 1502. The one or more headers include a QoS value 1504,an identifier 1506 of a 5G slice (i.e., a 5G slice identifier (ID)1506), and an identifier 1508 of a user group (i.e., a user group ID1508, which may be an SGT).

In summary, conventionally, in an enterprise network, enterprisesegmentation and transport services are limited to an enterpriseoverlay. Extending those services end-to-end across the enterprisenetwork and software defined (SD) WAN (SDWAN) is critical to theenterprise network for service assurance, and to a service provider fordifferentiation of their network offerings. To overcome theabove-mentioned limitation, embodiments presented herein extend theenterprise segmentation and transport services from the enterprisenetwork into a service provider network through automation ofprovisioning 5G slices by the enterprise network, and define animplementation in a segment routing underlay for 5G slices. Thus, theembodiments combine the provisioning and deployment of enterprisesegmentation policy, service layer agreement (SLA), and 5G slices acrossthe heterogeneous enterprise and SP networks, end-to-end. This extendsenterprise network service provisioning to the SP network, forconsistent quality of experience, regardless of access method (SP 5G orenterprise access). The embodiments provide a process for automatingprovisioning of SP 5G slices using an SR underlay, a process fordistribution of user group association to policy and network slice, anda process for distribution of endpoint device identity between theenterprise network and the SP network to map identity to group policy toprovide consistent quality of experience.

In summary, in one form, a method is provided comprising: by anenterprise controller of an enterprise network: sending to a servicegateway of a service provider network a request for network sliceinformation about network slices provisioned on a data plane of theservice provider network; responsive to the sending, receiving, from theservice gateway the network slice information including identifiers ofthe network slices and properties associated with the network slices;and responsive to receiving a request for the network slice informationfrom a network device at a border of a forwarding plane of theenterprise network, sending the network slice information to the networkdevice to cause the network device to perform configuring networktraffic in the forwarding plane with identifiers of ones of the networkslices that match the network traffic, and to perform forwarding thenetwork traffic configured with the identifiers of the ones of thenetwork slices to the data plane of the service provider network.

In another form, an apparatus is provided comprising: a networkinterface unit; and a processor of an enterprise controller of anenterprise network coupled to the network interface unit and configuredto perform: sending to a service gateway of a service provider network arequest for network slice information about network slices provisionedon a data plane of the service provider network; responsive to thesending, receiving, from the service gateway the network sliceinformation including identifiers of the network slices and propertiesassociated with the network slices; and responsive to receiving arequest for the network slice information from a network device at aborder of a forwarding plane of the enterprise network, sending thenetwork slice information to the network device to cause the networkdevice to perform configuring network traffic in the forwarding planewith identifiers of ones of the network slices that match the networktraffic, and to perform forwarding the network traffic configured withthe identifiers of the ones of the network slices to the data plane ofthe service provider network.

In a further form, a non-transitory computer readable storage medium isprovided. The One or more non-transitory computer readable media areencoded with instructions that, when executed by one or more processors,cause the one or more processors to perform, by an enterprise controllerof an enterprise network: sending to a service gateway of a serviceprovider network a request for network slice information about networkslices provisioned on a data plane of the service provider network;responsive to the sending, receiving, from the service gateway thenetwork slice information including identifiers of the network slicesand properties associated with the network slices; and responsive toreceiving a request for the network slice information from a networkdevice at a border of a forwarding plane of the enterprise network,sending the network slice information to the network device to cause thenetwork device to perform configuring network traffic in the forwardingplane with identifiers of ones of the network slices that match thenetwork traffic, and to perform forwarding the network trafficconfigured with the identifiers of the ones of the network slices to thedata plane of the service provider network.

In yet another form, a system is provided comprising: a network deviceat a border of a forwarding plane of an enterprise network; and anenterprise controller of the enterprise network and configured toperform: sending to a service gateway of a service provider network arequest for network slice information about network slices provisionedon a data plane of the service provider network; responsive to thesending, receiving, from the service gateway the network sliceinformation including identifiers of the network slices and propertiesassociated with the network slices; and responsive to receiving arequest for the network slice information from the network device,sending the network slice information to the network device; wherein thenetwork device is configured to perform: responsive to the network sliceinformation, configuring network traffic in the forwarding plane withidentifiers of ones of the network slices that match the networktraffic; and forwarding the network traffic configured with theidentifiers of the ones of the network slices to the data plane of theservice provider network.

Although the techniques are illustrated and described herein as embodiedin one or more specific examples, it is nevertheless not intended to belimited to the details shown, since various modifications and structuralchanges may be made within the scope and range of equivalents of theclaim.

What is claimed is:
 1. A method comprising: by an enterprise controllerof an enterprise network: sending to a service gateway of a serviceprovider network a request for network slice information about networkslices provisioned on a data plane of the service provider network;maintaining first mappings of user groups for network traffic of theenterprise network to traffic policies to be applied to the networktraffic; determining second mappings of the user groups to ones of thenetwork slices that match the user groups based on the traffic policiesand properties associated with the network slices; responsive to thesending, receiving, from the service gateway, the network sliceinformation including identifiers of the network slices and theirproperties; and responsive to receiving a request for the network sliceinformation from a network device at a border of a forwarding plane ofthe enterprise network, sending the network slice information and thesecond mappings to the network device to cause the network device toperform configuring the network traffic in the forwarding plane withidentifiers of ones of the network slices that match the network trafficbased on the second mappings, and to perform forwarding the networktraffic configured with the identifiers of the ones of the networkslices to the data plane of the service provider network.
 2. The methodof claim 1, wherein the network slices are 3^(rd) Generation PartnershipProject (3GPP) 5G slices, and the network slice information includes 5Gslice information, such that the identifiers of the network slicesinclude identifiers of the 5G slices and the properties includeproperties of the 5G slices.
 3. The method of claim 1, wherein, at thenetwork device, the configuring the network traffic includes:determining the ones of the network slices that match the networktraffic based on the traffic policies associated with the networktraffic as defined in the enterprise network and the propertiesassociated with the network slices; and applying the identifiers of theones of the network slices to the network traffic based on thedetermining the ones of the network slices.
 4. The method of claim 3,wherein the determining the ones of the network slices includesdetermining the ones of the network slices based on Quality-of-Services(QoS) values associated with the traffic polices.
 5. The method of claim3, wherein: the determining the ones of the network slices includesdetermining that latency, bandwidth, quality, and virtualized networkfunction (VNF) of the network slices match first, second, third, andfourth traffic policies of the traffic policies associated with thenetwork traffic; and the applying includes applying identifiers of thelatency, bandwidth, quality, and VNF network slices to the networktraffic associated with the first, second, third, and fourth trafficpolicies, respectively.
 6. The method of claim 1, further comprising, atthe data plane of the service provider network: receiving from theforwarding plane of the enterprise network the network trafficconfigured with the identifiers of the ones of the network slices; andsteering the network traffic to segment routes of the data plane of theservice provider network that implement the network slices according tothe identifiers of the ones of the network slices.
 7. The method ofclaim 1, further comprising, at the enterprise controller: sending tothe service gateway the first mappings and the second mappings forsending of the first mappings and the second mappings by the servicegateway to control functions of the service provider network responsiblefor controlling and monitoring the network traffic in the data plane ofthe service provider network based on the first mappings and the secondmappings.
 8. The method of claim 7, wherein the control functionsinclude a segment routing controller and a policy monitoring and billingmanager of the service provider network, and the method furthercomprises: at the segment routing controller, configuring the data planeof the service provider network using the first mappings and the secondmappings; and at the policy monitoring and billing manager, using thefirst mappings and the second mappings to maintain enterprise user groupsessions in the service provider network for monitoring and billing ofnetwork usage by network traffic traversing the data plane of theservice provider network.
 9. The method of claim 7, wherein the firstmappings include tuples of a form [user group, traffic policy] and thesecond mappings include tuples of a form [user group, network slice].10. The method of claim 7, wherein: at the service gateway, the sendingof the first mappings and the second mappings includes sending thesecond mappings to a segment routing controller of the control functionsof the service provider network that is responsible for configuring thedata plane of the service provider network; and the method furthercomprises, at the segment routing controller, configuring the data planeof the service provider network with the second mappings to cause thedata plane to steer the network traffic, when the network traffictraverses the data plane, based on the second mappings.
 11. The methodof claim 1, wherein the first mappings include tuples of a form [usergroup, traffic policy] and the second mappings include tuples of a form[user group, network slice].
 12. The method of claim 1, wherein, at thenetwork device: the configuring the network traffic includes applying,to the network traffic, identifiers of the user groups that are mappedto the ones of the network slices as indicated in the second mappings;and the forwarding includes forwarding the network traffic configuredwith the identifiers of the ones of the network slices and theidentifiers of the user groups mapped to the ones of the network slices.13. The method of claim 12, wherein the identifiers of the user groupsinclude security group tags.
 14. The method of claim 1, furthercomprising, at the enterprise controller: receiving from an identityservices engine an identity of a mobile device associated with theenterprise network; forwarding a device identity register request to anidentity-and-authentication service function of the service providernetwork, through the service gateway, the device identity registerrequest including the identity; receiving from theidentity-and-authentication service function, through the servicegateway, a response to the device identity register request includingthe identity and an indicator that the identity was authenticatedsuccessfully; and responsive to the response, storing the indicatorlinked to the identity.
 15. An apparatus comprising: a network interfaceunit; and a processor of an enterprise controller of an enterprisenetwork coupled to the network interface unit and configured to perform:sending to a service gateway of a service provider network a request fornetwork slice information about network slices provisioned on a dataplane of the service provider network; maintaining first mappings ofuser groups for network traffic of the enterprise network to trafficpolicies to be applied to the network traffic; determining secondmappings of the user groups to ones of the network slices that match theuser groups based on the traffic policies and properties associated withthe network slices; responsive to the sending, receiving, from theservice gateway, the network slice information including identifiers ofthe network slices and their properties; and responsive to receiving arequest for the network slice information from a network device at aborder of a forwarding plane of the enterprise network, sending thenetwork slice information and the second mappings to the network deviceto cause the network device to perform configuring the network trafficin the forwarding plane with identifiers of ones of the network slicesthat match the network traffic based on the second mappings, and toperform forwarding the network traffic configured with the identifiersof the ones of the network slices to the data plane of the serviceprovider network.
 16. The apparatus of claim 15, wherein the networkslices are 3^(rd) Generation Partnership Project (3GPP) 5G slices, andthe network slice information includes 5G slice information, such thatthe identifiers of the network slices include identifiers of the 5Gslices and the properties include properties of the 5G slices.
 17. Theapparatus of claim 15, wherein the processor is further configured toperform: sending to the service gateway the first mappings and thesecond mappings for sending of the first mappings and the secondmappings by the service gateway to control functions of the serviceprovider network responsible for controlling and monitoring the networktraffic in the data plane of the service provider network based on thefirst mappings and the second mappings.
 18. A system comprising: anetwork device at a border of a forwarding plane of an enterprisenetwork; and an enterprise controller of the enterprise network andconfigured to perform: sending to a service gateway of a serviceprovider network a request for network slice information about networkslices provisioned on a data plane of the service provider network;maintaining first mappings of user groups for network traffic of theenterprise network to traffic policies to be applied to the networktraffic; determining second mappings of the user groups to ones of thenetwork slices that match the user groups based on the traffic policiesand properties associated with the network slices; responsive to thesending, receiving, from the service gateway, the network sliceinformation including identifiers of the network slices and theirproperties; and responsive to receiving a request for the network sliceinformation from the network device, sending the network sliceinformation and the second mappings to the network device; wherein thenetwork device is configured to perform: responsive to the network sliceinformation and the second mappings, configuring network traffic in theforwarding plane with identifiers of ones of the network slices thatmatch the network traffic based on the second mappings; and forwardingthe network traffic configured with the identifiers of the ones of thenetwork slices to the data plane of the service provider network. 19.The system of claim 18, wherein the network slices are 3^(rd) GenerationPartnership Project (3GPP) 5G slices, and the network slice informationincludes 5G slice information, such that the identifiers of the networkslices include identifiers of the 5G slices and the properties includeproperties associated with the 5G slices.
 20. The system of claim 18,wherein the network device is configured to perform the configuring thenetwork traffic by: determining the ones of the network slices thatmatch the network traffic based on the traffic policies associated withthe network traffic as defined in the enterprise network and theproperties associated with the network slices; and applying theidentifiers of the ones of the network slices to the network trafficbased on the determining the ones of the network slices.